@sudhakar and @ajoslin thanks for your help, this is finally ready to go!

@ProLoser Looks good to me & much cleaner than my initial proposal..

Landed in 0f65bd9

What does it do exactly? Are there docs for it?

Not really lol. I should expand the docblock. I was going to add a demo when I push the new build.

@Narretz Want to help me out an open a PR?

Here's basically how it works:

1. Put ui-route where you want to do something depending on what the current route is (such as setting an active class on a nav link or hiding something)
2. Declare a route-match pattern
3. [optional] Specify an ng-model to store the boolean into, otherwise it will store the boolean into $uiRoute
4. Use this boolean to perform your behavior: <a ng-class="{active:$uiRoute}"> or <div ng-hide="$uiRoute">
   • $uiRoute (or your specified model) is added to the scope and can be accessed from children

Declaring a route-match pattern

ui-route
Support regex and {{}}

<li ui-route="/dashboard">
or
<li ui-route="/user/[0-9]*">
or
<li ng-repeat="tab in tabs" ui-route="/{{tab}}">
or
<li ng-repeat="tab in tabs" ui-route="/{{tab}}(/[0-9]*)?">

ng-href
Supports {{}} statically

<a ng-href="/dashboard" ui-route>
or
<a ng-href="/user/{{userId}}" ui-route>

href
Static only

<a href="/dashboard" ui-route>

Working with the flag

<li ui-route="/dashboard" ng-class="{active:$uiRoute}">
  <a href="/dashboard">Dash</a>
  <ul>
    <li ui-route="/dashboard/stats" ng-model="isStatsRoute">
     <div ng-show="isStatsRoute && $uiRoute">

Yes it's a shitty example

@joseym Again, I'm not sure how much you're willing to take on, but if you are willing to help me out, The above comment ^^ needs to be turned into an open PR for the demo page that we can merge in once we push v0.4.0

It does not need to have an updated version of angular-ui in the PR as that will be changed already.

Sure, this is great.